Skip to content

test: use locally published version in E2E project setup #15052

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 15, 2019

Conversation

clydin
Copy link
Member

@clydin clydin commented Jul 11, 2019

This removes the need to perform a second special local build of the packages during the E2E test process.

This also has the benefit of causing CI to fail if the package versions in latest-versions.ts are not kept synchronized with the CLI package versions.

@clydin clydin added the target: major This PR is targeted for the next major release label Jul 11, 2019
@@ -18,7 +18,7 @@ packages:
access: $all
publish: $all

'@ngtools/*':
'@ngtools/webpack':
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Was this change necessary or was it just cleanup? Just wondering, because @angular-devkit/* still has the star above.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

“@ngtools/json-schema” is used by ng-packgr. Since it no longer exists, it’s not published locally which causes the installation of ng-packgr to fail within the E2E tests.

Copy link
Contributor

@filipesilva filipesilva left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes.

@mgechev mgechev merged commit 8d7ab42 into angular:master Jul 15, 2019
@clydin clydin deleted the e2e-cleanup branch July 15, 2019 16:51
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 13, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
target: major This PR is targeted for the next major release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants